Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The Cisco ASA must be configured to generate traffic log entries containing information to establish when (date and time) the events occurred.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-239856 | CASA-FW-000050 | SV-239856r665854_rule | Medium |
| Description |
|---|
| Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment, and provide forensic analysis of network traffic patterns, it is essential for security personnel to know when flow control events occurred (date and time) within the infrastructure. Associating event types with detected events in the network traffic logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element. |
| STIG | Date |
|---|---|
| Cisco ASA Firewall Security Technical Implementation Guide | 2024-06-06 |
Details
| Check Text ( C-43089r665852_chk ) |
|---|
| Verify that the logging timestamp command has been configured as shown below. logging enable logging timestamp If the ASA is not configured to generate traffic log entries containing information to establish when the events occurred, this is a finding. |
| Fix Text (F-43048r665853_fix) |
|---|
| Configure the ASA to generate traffic log entries containing information to establish when the events occurred. ASA(config)# logging timestamp |